Skip to content

Conversation

alocay
Copy link
Contributor

@alocay alocay commented Oct 1, 2025

Adding a step replace install script versions with RC build (if set), commit, push, and then tag. Afterwards it will update the install scripts again with the new release version.

@apollo-librarian
Copy link

apollo-librarian bot commented Oct 1, 2025

✅ Docs preview has no changes

The preview was not built because there were no changes.

Build ID: 33af1ecbc87b0a0b65245083
Build Logs: View logs

@alocay alocay changed the title Add rc version to install before tag Add rc version to install script before tag Oct 1, 2025
@alocay alocay changed the base branch from main to develop October 1, 2025 19:18
CURR_VERSION: ${{ steps.meta.outputs.rc_version != '' && steps.meta.outputs.rc_version || steps.meta.outputs.current_version }}
NEW_VERSION: ${{ steps.bump.outputs.new_version }}
run: |
python3 - <<'PY'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems copy/pasted from the other step where the RC is generated. It'd be nice if it could be reused and we just pass either the RC version or the new version into it but its probably fine if we want to refactor that later

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I was considering this as well. Let me see if there a way to do this and update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants